ci(backport): register workflow_dispatch trigger#4376
Conversation
Adds workflow_dispatch with pr_number + target_branch inputs so the backport workflow can be triggered manually from any branch. Job logic is unchanged: the existing 'if: github.event.pull_request.merged' guard makes dispatch on main a no-op. The trigger is needed on main so that follow-up branches with the full implementation can be tested via 'gh workflow run --ref <branch>'.
sveitser
requested review from
bfish713,
imabdulbasit,
jbearer,
lukaszrzasik and
ss-es
as code owners
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. |
|
Claude finished @sveitser's task in 53s —— View job Code Review: ci(backport): register workflow_dispatch trigger
Summary: This PR adds a Review: LGTM — this is a minimal, low-risk scaffolding change. One thing to be aware of (not a blocker): as-is, a manual dispatch of this workflow would be a no-op because the job's No issues found — the change is clean, correctly typed, and appropriately scoped. |
2 participants
I need workflow dispatch on
mainfor testing #4375